Medical Device with Automated Modality Switching

ABSTRACT

A medical device such as an infusion system detects that an accessory has been coupled to the device. The medical device initially operates in a first mode of operation. The medical device, in response to the detecting, associates the accessory with a different mode of operation for the medical device that requires changes to at least one of the operating parameters for the infusion system or elements within a graphical user interface. The medical device then automatically changes the mode of operation from the first mode of operation to the associated different mode of operation to reflect the coupling of the accessory to the infusion system. Related apparatus, systems, techniques and articles are also described.

TECHNICAL FIELD

The subject matter described herein relates to a medical device in whichits mode of operation automatically switches in response to the couplingof one or more accessories.

BACKGROUND

Medical devices such as infusion systems and ventilators are complex andmust operate under a variety of clinical conditions. Such medicaldevices may deliver multiple functionalities depending on thecircumstance including the patient, caregiver, and location. However,such functionalities are often dependent on the care to be administeredby the device. Most medical devices are not well equipped to respond toenvironmental cues and adapt to meet imminent needs of the care for thepatient.

SUMMARY

In one aspect, an infusion system detects that an accessory has beencoupled to the infusion system. The infusion system is configured toadminister medication to a patient and includes at least one dataprocessor, memory, and a display for rendering a graphical userinterface. Further, the infusion system initially operates in a firstmode of operation. The infusion system, in response to the detecting,associates the accessory with a different mode of operation for theinfusion system that requires changes to at least one of the operatingparameters for the infusion system or elements within the graphical userinterface. The infusion system then automatically changes the mode ofoperation from the first mode of operation to the associated differentmode of operation to reflect the coupling of the accessory to theinfusion system.

The accessory can take many different forms. Example accessories includea patient controlled analgesia (PCA) pump, a syringe pump, an enteralpump, an elastomeric pump, a peristaltic pump, a multi-channel pump, anda large volume pump.

The accessory can also be a tubing set through which the medicationflows to the patient.

The accessory can be a vital signs monitoring sensor.

The detecting can include detecting that the accessory is physicallyconnected to the infusion system. The detecting can include initiatingwireless communication between the accessory and the infusion system.

The detecting can also or additionally include various optical,electrical, electromechanical, magnetic and other switching/detectionmethodologies. For example, the coupling of the accessory to theinfusion system can be detected by an optical sensor integrated into theinfusion system. In such cases, the optical sensor can detect anindicator such as a bar code or optical pattern on the accessory. Inaddition, the coupling of the accessory to the infusion system can bedetected by a switch that is triggered upon mechanically coupling theaccessory to the infusion system. Further, the coupling of the accessoryto the infusion system can detected via electromagnetic fields orelectromagnetic induction.

The associating can include polling a remote computing device to receivedata to associate the detected accessory with the different mode ofoperation. Data can be received from the remote computing device thatspecifies parameters or restrictions regarding the administration ofmedication to the patient such that the different mode of operationtakes into account such specified parameters or restrictions. Theparameters regarding administration of medication to the patient caninclude a prescription for the patient. The restrictions regardingadministration of medication to the patient can be associated withallergies of the patient.

The changing can, in some cases, include polling a remote computingdevice to obtain a software or firmware update for the infusion system.

In another variation, a ventilator can detect that an accessory has beencoupled to the ventilator. The ventilator is configured to assist apatient with his or her breathing function and includes at least onedata processor, memory, and a display for rendering a graphical userinterface. The ventilator initially operates in a first mode ofoperation. Thereafter, the ventilator, in response to the detecting,associates the accessory with a different mode of operation for theventilator. The different mode of operation requires changes to at leastone of: operating parameters for the ventilator and elements within thegraphical user interface. Thereafter, the ventilator automaticallychanges the mode of operation from the first mode of operation to theassociated different mode of operation to reflect the coupling of theaccessory to the ventilator.

In still a further interrelated aspect, a medical device detects that anaccessory has been coupled to the medical device. The medical deviceincludes least one data processor, memory, and at least one mechanicallyactuatable element. In addition, the medical device initially operatesin a first mode of operation. The medical device, in response to thedetecting, associates the accessory with a different mode of operationfor the medical device. The different mode of operation requires changesto at least one operating parameter associated with the at least onemechanically actuatable element. Subsequently, the medical deviceautomatically changes the mode of operation from the first mode ofoperation to the associated different mode of operation to reflect thecoupling of the accessory to the medical device.

In yet a further interrelated aspect, a medical device system detectsthat an accessory has been coupled to the device. The medical deviceinitially operates in a first mode of operation. The medical device, inresponse to the detecting, associates the accessory with a differentmode of operation for the medical device that requires changes to atleast one of the operating parameters for the infusion system orelements within a graphical user interface. The medical device thenautomatically changes the mode of operation from the first mode ofoperation to the associated different mode of operation to reflect thecoupling of the accessory to the infusion system.

Non-transitory computer program products (i.e., physically embodiedcomputer program products) are also described that store instructions,which when executed by one or more data processors of one or morecomputing systems, causes at least one data processor to performoperations herein. Similarly, computer systems are also described thatmay include one or more data processors and memory coupled to the one ormore data processors. The memory may temporarily or permanently storeinstructions that cause at least one processor to perform one or more ofthe operations described herein. In addition, methods can be implementedby one or more data processors either within a single computing systemor distributed among two or more computing systems. Such computingsystems can be connected and can exchange data and/or commands or otherinstructions or the like via one or more connections, including but notlimited to a connection over a network (e.g. the Internet, a wirelesswide area network, a local area network, a wide area network, a wirednetwork, or the like), via a direct connection between one or more ofthe multiple computing systems, etc.

The subject matter described herein provides many technical advantages.For example, the current subject matter provides enhanced usability formedical devices such as infusion systems and ventilators byautomatically changing a mode of operation when an accessory is coupledto such medical devices.

The details of one or more variations of the subject matter describedherein are set forth in the accompanying drawings and the descriptionbelow. Other features and advantages of the subject matter describedherein will be apparent from the description and drawings, and from theclaims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a logic diagram illustrating a medical device;

FIG. 2 is a diagram illustrating a healthcare computing environment;

and

FIG. 3 is a process flow diagram illustrating automated switching ofoperating modalities of a medical device.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a block diagram 100 illustrating a medical device 110 used inconnection with the treatment of a patient. Example medical devices 110include, but are not limited to, infusion systems (i.e., systemsconfigured to administer fluid such as medication and food to a patient,etc.) and ventilators (i.e., systems configured to assist a patient withhis or her breathing function). The medical device 100 can include atleast one hardware data processor 111 (which can be a multi-coreprocessor) and memory 112 storing instructions for execution by the atleast one data processor. In addition, the medical device 110 caninclude a communications interface 113 which, depending on the desiredimplementation, can communicate with external devices/computer networksthat are physically connected to the medical device 110 and/or which arein direct or indirect communication with the medical device 110 via awired and/or wireless communications network.

The medical device 110 can additionally and optionally include at leastone mechanically actuatable element 114 that can have variable operatingmodes (e.g., variable speeds, active/non-active, etc.). Examples ofmechanically actuatable elements 114 include, for example, a pump usedfor infusion of fluids to a patient and a pump to deliver gas to apatient for breathing purposes.

The medical device 110 can also include a display 115 that renders agraphical user interface that characterizes various aspects regardingthe operation of the medical device 110. In some implementations, thegraphical user interface displayed in the display 115 includes aplurality of graphical user interface elements which, when activated viauser-generated input, causes either a mode of operation of the medicaldevice 110 to change and/or a view presented in the graphical userinterface of the display 115 to change. The user-generated input can bevia various modalities including, for example, the display 115 if itincludes a capacitive or other touch screen interface, mechanicalbuttons/knobs/sliders external to the display 115, and the like.

The medical device 110 can be coupled to one or more accessories 120that form part of the functionality offered by the medical device 110(e.g., change the manner in which the at least one mechanicallyactuatable elements operate 114, etc.) and/or which cause the graphicaluser interface (GUI) rendered within the display 115 to change (e.g., adifferent view can be displayed in the GUI, etc.). The accessories 120can take a wide variety of forms including components required for theoperation of the medical device 110, sensors for use by the medicaldevice 110, and/or other medical devices involved with thetreatment/care of a patient.

The accessories 120 can be coupled to the medical device 110 in avariety of manners. For example, the accessory 120 _(A) can be connectedby a wire/socket providing either unidirectional communication from theaccessory 120 _(A) to the medical device 110 or providing bi-directionalcommunication. For example, the accessory 120 _(A) can be a vital signsmonitor such as a pulse oximeter, a set of electrocardiogram electrodes(collectively ECG), heart rate monitor, blood pressure monitor, as wellas other types of physiological/vital sign monitors. In some cases, suchas with pulse oximeters, signals are transmitted from the accessory 120_(A) to the medical device 110 and not vice versa. With other cases, theaccessory 120 _(A) can receive signals from the medical device 110 suchas the activation of a blood pressure cuff

Similar to the hard-wired accessory 120 _(A), other accessories 120 _(B)and 120 _(D) can be coupled to the medical device 110 either directlyvia peer-to-peer unidirectional or bi-directional communication (as withaccessory 120 _(D)) or indirectly via unidirectional or bi-directionalcommunication over a network 130 (as with accessory 120 _(B)) which maybe wired and/or wireless. These accessories 120 _(B) and 120 _(D), whilenot directly connected to the medical device 110 can have similarfunctionality to the accessory 120 _(A) which is hard-wired to themedical device 110 (as described above). The network 130 can be, forexample, a local area Intranet, a hospital information system, theInternet, and the like.

In other cases, the accessory 120 _(C) can be physically connected tothe medical device 110 either directly or via an adapter or othermechanism. For example, in the case of the medical device 110, theaccessory 120 _(C) can be an infusion module such as a syringe pumpmodule, a patient controlled analgesia (PCA) module, an enteral pump, anelastomeric pump, a peristaltic pump, a multi-channel pump, or a largevolume pump. The accessory 120 _(C) can also be a disposable element foruse by the medical device 110 such as a tubing set or other adapter. Forexample, different tubing sets can, for example, implicate differentcaregiving modalities. Opaque tubing sets can be used in someapplications and/or some tubing sets can act as chemical barriers.Tubing sets can be coded, for example, by an RFID chip, a bar code, a QRcode, an optical code, or other, and identified by the medical device110 and the medical device 110 can automatically switch to theappropriate configuration for providing care to the patient. Forexample, a tubing set that is coded for use with a neonate, wouldautomatically switch the controls, alarms, settings, and other functionsappropriate for a neonate rather than an adult.

The accessory 120, need not be a tubing set but, rather, can take theform of disposables. For example, the accessory can be a disposableelement used for chemotherapy, a syringe for manual administration ofmedication, epidural disposable, enteral disposable, per-enteraldisposable as well as other types of equipment used to deliver fluid toa patient (in the case the case of infusion systems) or gas to a patient(in the case of ventilators).

The medical device 110 can detect the coupling of an accessory 120 toit. Coupling, in this regard (unless otherwise specifically specified),can include one or more of: the wired connection of an accessory 120_(A) to the medical device 110, the initiation of communication by themedical device 110 with an accessory 120 _(B) via a network, a directmechanical/physical coupling of an accessory 120 _(C) to the medicaldevice 110, or peer-to-peer communication between the medical device 110and an accessory 120 _(D). Upon this detection of the coupling of anaccessory 120, the medical device 110 can, in some cases, change a modeof operation of the medical device 110. This changing can be based, forexample, by accessing a local or remote (via the network 130) rulesengine/lookup table/server to determine whether or not any changes tothe mode of operation medical device 110 should occur in response to thedetection of the accessory 120 coupling.

The detection of the coupling can occur when the communicationsinterface 113 initiates communication by receiving data/signals from anaccessory 120 _(B, D) or by initiating bi-directional communication withan accessory 120 _(B, D). With the latter, there may be initialhandshaking/discovery which is used to initiate the communication andthe detection can be considered to occur once such discovery has beencompleted. Similar handshaking/discovering can occur in connection witha wired accessory 120 _(A) as part of establishing unidirectional orbidirectional communication (via the communications interface 113).

In some variations, the detection of the coupling of an accessory 120can cause an alarm to be triggered and/or to cause the medical device110 to cease operation. Such an arrangement is advantageous to avoidmisconnections or reconnections in which an accessory 120 isinadvertently connected to the wrong medical device 110 (either becauseof compatibility issues or particular patient care). For example, thecurrent subject matter can be used to detect the misconnection of an aircuff to an IV line. The alarms can be visual indicators (changes incolors to the GUI), audio indicators, and/or vibratory indicators.

In other variations, the detection of the coupling can occur when theaccessory 120 _(C) is being physically connected to the medical device110 or in physical proximity thereof. The physical connection can bedetected, for example, using a switch which is mechanically tripped whenthe accessory 120 _(C) is mechanically connected to the medical device110. In the addition or in the alternative, proximity sensors can formpart of the medical device 110 that can be used to detect when theaccessory 120 _(C) is coupled to the medical device 110. Other type ofproximity technologies can be used including integrated bar codescanners and other optical technologies, magnetic elements/switches,electromechanical element/switches and the like. In some variations, themedical device 110 can include a proximity sensor that detect acorresponding signal from the accessory via electromagneticfields/electromagnetic induction such as, Radio-Frequency Identification(RFID), Near Field Communication (NFC), and the like. In othervariations, the medical device 110 can include an optical sensor thatincludes an optical sensor to scan or otherwise capture a visualidentifier (e.g., bar code, optical pattern, etc.) on the accessory 120_(C) (or in some cases on an identifier worn by the patient).

After the detection, the medical device 110 can associate the coupledaccessory 120 with a different mode of operation and cause the medicaldevice 110 to commence operation according to such different modeoperation. The different mode of operation can include automaticallychanging one or more operating parameters of the medical device 110and/or changing elements within the GUI rendered in the display 115(i.e., a different GUI view can be displayed). This changing can, forexample, be automatic in that it is implemented by the medical device110 without any clinician intervention. In some variations, the GUIrendered in the display 115 can provide a prompt to a caregiver toapprove the change of the mode of operation of the medical device 110(upon the detection of coupling of the accessory 120).

In some cases, changing the mode of operation can include changing oneor more operating parameters associated with the mechanically actuatableelement(s) 114. For example, the mechanically actuatable element 114 canbe a pump that is used by the accessory 120 for various purposes such asfluid infusion or gas delivery to a patient. The changes in mode ofoperation can accommodate different flow rates, operating time periods,periodicity of operation, and the like.

In other variations, changing of the mode of operation can includeupdating software/firmware that is executed by the medical device 110.In such implementations, the medical device 110, in response to thedetection of the coupling of the accessory 120, can poll a remotecomputing system/device to indicate such coupling, and such remotecomputing system/device can reply with data encapsulating informationrequired for such an update of the software/firmware. For example, asoftware update can include a new/expanded drug library associated withthe accessory 120. This drug library can be obtained, for example, bypolling a hospital pharmacy system with an identification associatedwith the medical device 110 and/or the patient to ensure that the properdrugs/medication/treatment is administered to the patient. The softwareupdate can additionally/alternatively include data including aprescription for the patient obtained, for example, from the hospitalpharmacy system. The remote computing system/device can also provideinformation about permitted medications to be administered to thepatient as well as related concentrations, doses, and the like.Relatedly, information about allergies and/or medications which cannotbe mixed with prescribed medications can be provided. In addition or inthe alternative, the polling of the remote computing system can beimplemented to ensure, for example, that the medical device 110 islicensed to implement the corresponding operations/actions.

FIG. 2 is a system diagram illustrating a computing landscape 200 withina healthcare environment such as a hospital that includes one or medicaldevices 110 as described above. Various devices and systems, both localto the healthcare environment and remote from the healthcareenvironment, can interact via the network 130 (which can be one of aplurality of networks). The computing network 130 can provide any formor medium of digital communication connectivity (i.e., wired orwireless) amongst the various devices and systems. Examples ofcommunication networks include a local area network (“LAN”), a wide areanetwork (“WAN”), and the Internet. In some cases, one or more of thevarious devices and systems can interact directly via peer-to-peercoupling (either via a hardwired connection or via a wireless protocolsuch as BLUETOOTH, ZIGBEE, short range radio , WiFi, etc.). In addition,in some variations, one or more of the devices and systems communicatevia a cellular data network.

The medical devices 110 can each include at least one communicationsinterface 113 that can access the computing network 130 either via afixed wired connection or via a wireless connection (via, for example,one or more access points). In addition, the medical devices 110 canalso couple to other components within the computing landscape 200 viadirect wired or wireless peer-to-peer coupling (not shown). Furthermore,in some cases, the medical devices 110 can be self-contained and are notconnected to any other devices or networks. The medical devices 110 cantransmit data via the computing network 130 to any of the othercomponents within the landscape 200 that can, for example, characterizethe medical device 110. In addition, the medical devices 110 can receivedata from the computing network 130 relating to monitoring and in somecases controlling one or more attributes of the medical devices 110(e.g., software updates, configuration updates, historical data, statusinformation, assets location, patient information, etc.).

In particular, aspects of the computing landscape 200 can be implementedin a computing system that includes a back-end component (e.g., as adata server 210), or that includes a middleware component (e.g., anapplication server 215), or that includes a front-end component (e.g., aclient computer 220 having a graphical user interface or a Web browserthrough which a user may interact with an implementation of the subjectmatter described herein), or any combination of such back-end,middleware, or front-end components. A client 220 and server 210, 215are generally remote from each other and typically interact through thecommunications network 130. The relationship of the clients 220 andservers 210, 215 arises by virtue of computer programs running on therespective computers and having a client-server relationship to eachother. Clients 220 can be any of a variety of computing platforms thatinclude local applications for providing various functionality withinthe healthcare environment. Example clients 220 include, but are notlimited to, desktop computers, laptop computers, tablets, and othercomputers with touch-screen interfaces. The local applications can beself-contained in that they do not require network connectivity and/orthey can interact with one or more of the servers 210, 215 (e.g., a webbrowser).

A variety of applications can be executed on the various devices andsystems within the computing landscape including the medical devices 110such as electronic health record applications, medical devicemonitoring, operation, and maintenance applications, schedulingapplications, billing applications and the like. As another example, theapplications can comprise a collection of enterprise-based applicationsthat provide dose error reduction software (DERS) for the medicaldevices 110 incorporates a role-based view of infusion data, provides acomprehensive platform for connectivity to external hospitalapplications, and enables directed maintenance and calibrationactivities for devices, storage of clinical and device history, etc. Asa further example, the applications can provide for remote alarmsmanagement and/or asset tracking for the medical devices 110.

The network 130 can be coupled to one or more data storage systems 225.The data storage systems 225 can include databases providing physicaldata storage within the healthcare environment or within a dedicatedfacility. In addition, or in the alternative, the data storage systems225 can include cloud-based systems providing remote storage of data in,for example, a multi-tenant computing environment. The data storagesystems 225 can also comprise non-transitory computer readable media.

Mobile communications devices (MCDs) 230 can also form part of thecomputing landscape 200. The MCDs 230 can communicate directly via thenetwork 130 and/or they can communicate with the network 130 via anintermediate network such as a cellular data network. Various types ofcommunication protocols can be used by the MCDs 230 including, forexample, messaging protocols such as SMS and MMS. In some cases, theMCDs 230 can receive alerts generated from the operation of the medicaldevices 110 and/or they can otherwise be used to monitor the operationof such medical devices 110.

Various types of medical devices 110 can be used as part of thecomputing landscape 200. These medical devices 110 can comprise, unlessotherwise specified, any type of device or system with a communicationsinterface that characterizes one or more physiological measurements of apatient and/or that characterize or are used for the treatment of apatient. In some cases, the accessories 120 communicate via peer to peerwired or wireless communications with a medical device 110 (as opposedto communicating with the network 130). For example, the accessory 120can comprise a bedside vital signs monitor that is connected to amedical device 110. One or more attributes of the medical devices 110can be locally controlled by a clinician, controlled via a clinician viathe network 130, and/or they can be controlled by one or more of aserver 210, 215, a client 220, or a MCD 230.

The computing landscape 200 can provide various types of functionalityas may be required within a healthcare environment such as a hospital.For example, a pharmacy can initiate a prescription via one of theclient computers 220. This prescription can be stored in the datastorage 225 and/or pushed out to other clients 220, an MCD 230, and/orone or more of the medical devices 110. In addition, the medical devices110 can provide data characterizing one or more physiologicalmeasurements of a patient and/or treatment of a patient (e.g., medicaldevice 110 can be an infusion management system, etc.). The datagenerated by the medical devices 110 can be communicated to othermedical devices 110, the servers 210, 215, the clients 220, the MCDs230, and/or stored in the data storage systems 225.

Various methods can be implemented in accordance with the currentsubject matter. FIG. 3 is a process flow diagram 300 in which, at 310, amedical device, such as an infusion system or a ventilator, detects thatan accessory has been coupled to it. The medical device includes atleast one data processor, memory, and a display for rendering agraphical user interface and initially operates in a first mode ofoperation. Thereafter, at 320, the medical device associates, inresponse to the detecting, the accessory with a different mode ofoperation for the infusion system. The different mode of operation canchanges at least one of: operating parameters for the infusion system orelements within the graphical user interface. Subsequently, at 330, themode of operation of the medical device is automatically changed fromthe first mode of operation to the associated different mode ofoperation to reflect the coupling of the accessory to the medicaldevice.

In the descriptions above and in the claims, phrases such as “at leastone of” or “one or more of” may occur followed by a conjunctive list ofelements or features. The term “and/or” may also occur in a list of twoor more elements or features. Unless otherwise implicitly or explicitlycontradicted by the context in which it is used, such a phrase isintended to mean any of the listed elements or features individually orany of the recited elements or features in combination with any of theother recited elements or features. For example, the phrases “at leastone of A and B;” “one or more of A and B;” and “A and/or B” are eachintended to mean “A alone, B alone, or A and B together.” A similarinterpretation is also intended for lists including three or more items.For example, the phrases “at least one of A, B, and C;” “one or more ofA, B, and C;” and “A, B, and/or C” are each intended to mean “A alone, Balone, C alone, A and B together, A and C together, B and C together, orA and B and C together.” In addition, use of the term “based on,” aboveand in the claims is intended to mean, “based at least in part on,” suchthat an unrecited feature or element is also permissible.

One or more aspects or features of the subject matter described hereinmay be realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations may include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device (e.g., mouse, touch screen, etc.), andat least one output device.

These computer programs, which can also be referred to programs,software, software applications, applications, components, or code,include machine instructions for a programmable processor, and can beimplemented in a high-level procedural language, an object-orientedprogramming language, a functional programming language, a logicalprogramming language, and/or in assembly/machine language. As usedherein, the term “machine-readable medium” refers to any computerprogram product, apparatus and/or device, such as for example magneticdiscs, optical disks, memory, and Programmable Logic Devices (PLDs),used to provide machine instructions and/or data to a programmableprocessor, including a machine-readable medium that receives machineinstructions as a machine-readable signal. The term “machine-readablesignal” refers to any signal used to provide machine instructions and/ordata to a programmable processor. The machine-readable medium can storesuch machine instructions non-transitorily, such as for example as woulda non-transient solid state memory or a magnetic hard drive or anyequivalent storage medium. The machine-readable medium can alternativelyor additionally store such machine instructions in a transient manner,such as for example as would a processor cache or other random accessmemory associated with one or more physical processor cores.

With certain aspects, to provide for interaction with a user, thesubject matter described herein can be implemented on a computer havinga display device, such as for example a cathode ray tube (CRT) or aliquid crystal display (LCD) monitor for displaying information to theuser and a keyboard and a pointing device, such as for example a mouseor a trackball, by which the user may provide input to the computer.Other kinds of devices can be used to provide for interaction with auser as well. For example, feedback provided to the user can be any formof sensory feedback, such as for example visual feedback, auditoryfeedback, or tactile feedback; and input from the user may be receivedin any form, including, but not limited to, acoustic, speech, or tactileinput. Other possible input devices include, but are not limited to,touch screens or other touch-sensitive devices such as single ormulti-point resistive or capacitive trackpads, voice recognitionhardware and software, optical scanners, optical pointers, digital imagecapture devices and associated interpretation software, and the like.

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

The subject matter described herein can be embodied in systems,apparatus, methods, and/or articles depending on the desiredconfiguration. The implementations set forth in the foregoingdescription do not represent all implementations consistent with thesubject matter described herein. Instead, they are merely some examplesconsistent with aspects related to the described subject matter.Although a few variations have been described in detail above, othermodifications or additions are possible. In particular, further featuresand/or variations can be provided in addition to those set forth herein.For example, the implementations described above can be directed tovarious combinations and subcombinations of the disclosed featuresand/or combinations and subcombinations of several further featuresdisclosed above. In addition, the logic flow(s) depicted in theaccompanying figures and/or described herein do not necessarily requirethe particular order shown, or sequential order, to achieve desirableresults. Other implementations may be within the scope of the followingclaims.

What is claimed is:
 1. A method comprising: detecting, by an infusionsystem, that an accessory has been coupled to the infusion system, theinfusion system being configured to administer medication to a patientand comprising at least one data processor, memory, and a display forrendering a graphical user interface, the infusion system initiallyoperating in a first mode of operation; associating, by the infusionsystem in response to the detecting, the accessory with a different modeof operation for the infusion system, wherein the different mode ofoperation requires changes to at least one of: operating parameters forthe infusion system or elements within the graphical user interface; andautomatically changing, by the infusion system, the mode of operationfrom the first mode of operation to the associated different mode ofoperation to reflect the coupling of the accessory to the infusionsystem.
 2. The method of claim 1, wherein the detecting comprises:detecting that the accessory is physically connected to the infusionsystem.
 3. The method of claim 1, wherein the detecting comprises:initiating wireless communication between the accessory and the infusionsystem.
 4. The method of claim 1, wherein the accessory is selected froma group consisting of: a patient controlled analgesia (PCA) pump, asyringe pump, an enteral pump, an elastomeric pump, a peristaltic pump,a multi-channel pump, or a large volume pump.
 5. The method of claim 1,wherein the accessory is a tubing set through which the medication flowsto the patient.
 6. The method of claim 1, wherein the accessory is avital signs monitoring sensor.
 7. The method of claim 1, wherein thecoupling of the accessory to the infusion system is detected by anoptical sensor integrated into the infusion system.
 8. The method ofclaim 7, wherein the optical sensor detects a bar code or opticalpattern on the accessory.
 9. The method of claim 1, wherein the couplingof the accessory to the infusion system is detected by a switch that istriggered upon mechanically coupling the accessory to the infusionsystem.
 10. The method of claim 1, wherein the coupling of the accessoryto the infusion system is detected via electromagnetic fields orelectromagnetic induction.
 11. The method of claim 1, wherein theassociating comprises: polling a remote computing device to receive datato associate the detected accessory with the different mode ofoperation.
 12. The method of claim 11 further comprising: receiving datafrom the remote computing device specifying parameters or restrictionsregarding the administration of medication to the patient, wherein thedifferent mode of operation takes into account such specified parametersor restrictions.
 13. The method of claim 12, wherein the parametersregarding administration of medication to the patient comprise aprescription for the patient.
 14. The method of claim 12, wherein therestrictions regarding administration of medication to the patient areassociated with allergies of the patient.
 15. The method of claim 1,wherein the changing comprises: polling a remote computing device toobtain a software or firmware update for the infusion system.
 16. Amethod comprising: detecting, by a ventilator, that an accessory hasbeen coupled to the ventilator, the ventilator being configured toassist a patient with his or her breathing function and comprising atleast one data processor, memory, and a display for rendering agraphical user interface, the ventilator initially operating in a firstmode of operation; associating, by the ventilator in response to thedetecting, the accessory with a different mode of operation for theventilator, wherein the different mode of operation requires changes toat least one of: operating parameters for the ventilator or elementswithin the graphical user interface; and automatically changing, by theventilator, the mode of operation from the first mode of operation tothe associated different mode of operation to reflect the coupling ofthe accessory to the ventilator.
 17. A method comprising: detecting, bya medical device, that an accessory has been coupled to the medicaldevice, the medical device comprising at least one data processor,memory, and at least one mechanically actuatable element, the medicaldevice initially operating in a first mode of operation; associating, bythe medical device in response to the detecting, the accessory with adifferent mode of operation for the medical device, wherein thedifferent mode of operation requires changes to at least one operatingparameter associated with the at least one mechanically actuatableelement; and automatically changing, by the medical device, the mode ofoperation from the first mode of operation to the associated differentmode of operation to reflect the coupling of the accessory to themedical device.